Structure for a system and method of predicting power events in an intermittent power environment and dispatching computational operations of an integrated circuit accordingly

ABSTRACT

A design structure for a system and method of predicting power events in intermittent power environments and dispatching computational operations of an integrated circuit accordingly. A power management prediction system includes a controller executing a prediction algorithm, an arrangement of computation circuitry, a non-volatile storage device containing a power requirements log and a power history log, a clock generator, an intermittent power source, and a power monitor circuit. A method of predicting intermittent power events and dispatching computational operations includes: storing power requirements of each computational operation, monitoring the intermittent power source to generate a history log, predicting a subsequent power event based on the history log, retrieving actual power requirements of one or more computational operations, comparing the predicted power event with actual power requirements, determining whether actual power requirements are satisfied, dispatching one or more computational operations that correspond to one or more actual power events, or performing an error recovery operation.

FIELD OF THE INVENTION

The present invention generally relates to the field of integrated circuits that operate in an intermittent power environment. In particular, the present invention is directed to a design structure for a system for and method of predicting power events in an intermittent power environment and dispatching computational operations of an integrated circuit accordingly.

BACKGROUND

In many contexts the use of batteries, large capacitors, or other constant power sources is impractical due to cost, weight, size, capability, and other factors. Environmental scavenging of power or energy may provide an alternative to such constant power sources. However, such environmental power sources may not be continuous i.e., they provide an intermittent or periodic power environment. For example, remote sensing devices may operate via solar power, which may be variable. In another example, radio frequency identification (RFID) tag devices may be energized via RF pulses, that occur intermittently rather than continuously.

Due to the unknown signature and unpredictability of intermittent power sources, power storage in an integrated circuit device may not be realistic in certain intermittent power environments. For example, in certain conditions the power from an intermittent power source may not be of sufficient duration to power a selected computational operation within an integrated circuit. Therefore, in intermittent power environments, one must consider the paradigm of intermittent processing and inherent associated problems. One such problem is how to determine the best sequence of processes to execute in a given power cycle and, thereby, maximize the operation of an integrated circuit device in a given power cycle.

SUMMARY OF THE DISCLOSURE

In one embodiment, a design structure embodied in a machine readable medium used in a design process of a power management prediction system for use with a power source that produces power events is provided. The design structure of the system includes a monitor connectable to the power source for monitoring the power source and producing a power history table of power events previously produced by the power source; computation circuitry; a power requirements table containing power requirements information for the computational circuitry; and a controller connected to the computation circuitry, the power history table and the power requirements table, the controller calculating a predicted power cycle based on the power events in the power history table and enabling power to the computation circuitry based on the predicted power cycle and the power requirements information.

In another embodiment, a design structure embodied in a computer readable medium for performing a method of managing power prediction for computational operations is provided. The design structure includes a means for storing a set of power requirements for one or more computational operations; a means for monitoring a power source and creating a power history table of power events previously produced by the power source; a means for predicting a subsequent power event based on power events in the power history table; a means for retrieving the set of power requirements for one or more computational operations; and a means for comparing the set of power requirements with power events in the power history table to determine if the set of power requirements are met for one or more computational operations.

BRIEF DESCRIPTION OF THE DRAWINGS

For the purpose of illustrating the invention, the drawings show aspects of one or more embodiments of the invention. However, it should be understood that the present invention is not limited to the precise arrangements and instrumentalities shown in the drawings, wherein:

FIG. 1 illustrates a functional block diagram of a power management prediction system for operating in an intermittent power environment;

FIGS. 2A and 2B illustrate first and second process dispatch tables, respectively, for a first power sequence;

FIGS. 3A, 3B, and 3C illustrate first, second, and third process dispatch tables, respectively, for a second power sequence;

FIG. 4 is a flow diagram of a method of predicting power events in an intermittent power environment and dispatching computational operations by use of the power management prediction system of FIG. 1; and

FIG. 5 is a flow diagram of a design process used in semiconductor design, manufacturing, and/or test.

DETAILED DESCRIPTION

The present invention is directed to a design structure for a system for and method of predicting power events in an intermittent power environment and dispatching computational operations of an integrated circuit accordingly. The present disclosure provides a low-power architecture system that accepts intermittent or periodic power inputs with an unknown signature. The present disclosure also provides a method of predicting the most efficient dispatching of the intermittent power.

FIG. 1 illustrates a functional block diagram of one embodiment of a power management prediction system 20 for operating in an intermittent power environment. Power management prediction system 20 may be implemented within an integrated circuit 22 or any electronic device operating in the intermittent power environment. In one example, integrated circuit 22 may be, but is not limited to, an RFID tag, that is a wireless microchip upon which data or information is stored, for example, a unique digital identification number, as is well known in the art. The microchip of the RFID tag may be attached to an antenna (not shown) and, thus, the RFID tag is energized (i.e., powered) via RF pulses, which may occur intermittently rather than continuously. Thus, RF pulses are merely one example of an intermittent power source.

Integrated circuit 22 may include a controller 24, an arrangement of computation circuitry 26, a storage device 28, a clock generator 30, and a power monitor circuit 34. Integrated circuit 22 may be connected with an intermittent power source 32. It should also be noted that intermittent power source 32 may be part of integrated circuit 22 in another embodiment of the present disclosure, while keeping within the spirit and scope of the present disclosure. Controller 24 may further include a prediction algorithm 36; computation circuitry 26 may further include a plurality of sub-units 38 and a plurality of switches 40; storage device 28 may further include a power requirements table 42 and a power history table 44; and power monitor circuit 34 may further include, in one example, a resistor 46, a load 48, an analog-to-digital (A/D) converter 50, and a monitor logic 52.

Controller 24 may be any arrangement of standard control logic for handling the overall operation of integrated circuit 22 of power management prediction system 20. In one example, controller 24 may include a state machine for implementing prediction algorithm 36. Prediction algorithm 36 may be an algorithm for analyzing the power sequence of intermittent power source 32 and dispatching computational operations of integrated circuit 22 in a manner that maximizes the operation of integrated circuit 22 in any given power cycle of intermittent power source 32. More details of the operations of prediction algorithm 36 are provided with reference to FIGS. 2A, 2B, 3A, 3B, 3C, and 4.

By way of example, the computational operations of integrated circuit 22 are represented by the plurality of sub-units 38 of computation circuitry 26. More specifically, FIG. 1 shows, for example, but is not limited to, sub-units 38 a, 38 b, 38 c, 38 d, 38 e, 38 f, 38 g, through 38 n. Sub-units 38 a through 38 n may be connected in parallel or in series. Additionally, each sub-unit 38 has an associated switch 40, which is an electronic switch for controlling the power of each sub-unit 38, i.e. turning the power ON or OFF to each sub-unit 38. By way of example, FIG. 1 shows a set of switches 40 a, 40 b, 40 c, 40 d, 40 e, 40 f, 40 g, through 40 n associated with sub-units 38 a, 38 b, 38 c, 38 d, 38 e, 38 f, 38 g, through 38 n, respectively.

Storage device 28 may be any low-power non-volatile memory device, such as, but not limited to, a ferroelectric random access memory device (FRAM) of the type sold by Ramtron International Corporation (Colorado Springs, Colo.). The storage capacity of storage device 28 should generally be large to store the information of power requirements table 42 and power history table 44.

Power requirements table 42, which may be stored in storage device 28, contains the minimum power requirement of each computational operation of integrated circuit 22, such as the minimum power requirement of each sub-unit 38 of computation circuitry 26. Because the power requirements of each computational operation is known, the information of power requirements table 42 may be supplied, for example, by the designer of integrated circuit 22. The power requirements may be stored in the form of any user-defined power unit, such as a certain minimum power value (e.g., 10 or 20 milliwatts), that is supplied for one or more user-defined time increments (e.g., a millisecond or a microsecond). For example, if one power unit is defined as 10 milliwatts for a duration of one millisecond and sub-unit 38 a requires 20 milliwatts for three milliseconds, then sub-unit 38 a requires two power units per each of the three millisecond or a total of six power units (i.e., 2×3=6 power units).

Power history table 44, which may be stored in storage device 28, contains a running log of all power events produced by intermittent power source 32. Each power event of intermittent power source 32 may be, for example, a sequence of power pulses (i.e., power cycles), where each power cycle may be of a certain power intensity and may endure for a certain period of time. In one example, the contents of power history table 44 may include, but is not limited to, a peak value, a peak-to-end value, a start-to-peak value, and the number of peaks of the output voltage of intermittent power source 32. More details of the contents and use of power requirements table 42 and power history table 44 are provided with reference to FIGS. 2A, 2B, 3A, 3B, 3C, and 4.

Clock generator 30 may be any standard clock generator for generating an internal clock of any predetermined frequency to the components of integrated circuit 22, such as controller 24, computation circuitry 26, storage device 28, intermittent power source 32, and power monitor circuit 34. Because the frequency of clock generator 30 is known, the clock cycles of clock generator 30 provide a known time reference within integrated circuit 22.

Intermittent power source 32 may be any power source that is periodic and/or not constant, such as any power source that uses naturally occurring or man-made phenomenon. For example, intermittent power source 32 may be, but is not limited to, a solar-based source such as a photovoltaic array; a fluid dynamics-based source such as a bloodstream or water; a vibration-based source such as a spring or a tuning fork; a wind-based source such as a wind turbine; or, in the case of integrated circuit 22 being an RFID tag, an RF-based source; all of which may be intermittent power sources because they provide energy periodically and not continuously. The output of intermittent power source 32 is typically, but not necessarily, electrically connected to all active components of integrated circuit 22, such as to controller 24, computation circuitry 26, storage device 28, clock generator 30, and power monitor circuit 34.

Power monitor circuit 34 may be any known circuit for measuring a power source over time. The specific instance of power monitor circuit 34 that is shown in FIG. 1 is only exemplary. In the example of FIG. 1, one side of resistor 46, which may be a one-ohm resistor, is electrically connected to the output of intermittent power source 32. The opposite side of resistor 46 is electrically connected to load 48, which may be any highly resistive load. A/D converter 50 is electrically connected across resistor 46 and converts the analog voltage across resistor 46 to a digital value. The digital output of A/D converter 50 feeds an input of monitor logic 52. Monitor logic 52 may be digital logic that is used to accumulate data regarding the output of intermittent power source 32 over time (e.g., accumulate voltage data across or current data through resistor 46) over one or more time periods as determined, for example, by counting clock cycles of clock generator 30 in order to establish a time reference and/or duration. The data that is accumulated by monitor logic 52 is fed into and stored within power history table 44 in storage device 28. Thus, a representation of the characteristics of the power cycles generated by intermittent power source 32 may be captured for subsequent analysis by prediction algorithm 36.

Referring again to FIG. 1, the operation of power management prediction system 20 is as follows. The power requirements of sub-units 38 of computation circuitry 26 may be preloaded into power requirements table 42 of storage device 28. Power management prediction system 20 experiences a “learning” operation by which the characteristics of a sequence of multiple power cycles of intermittent power source 32 are captured by power monitor circuit 34 and stored in power history table 44 of storage device 28. A time reference for the sequence of multiple power cycles of intermittent power source 32 may be provided by use of clock generator 30. Subsequently, prediction algorithm 36 of controller 24 performs an analysis of the contents of power history table 44 in order to determine the time duration and intensity of each power cycle and, thus, determine whether a repeatable sequence of power cycles has occurred. Assuming that a repeatable power sequence is detected, prediction algorithm 36, in combination with controller 24, determines which sub-unit 38 may be executed in a given power cycle of the power sequence by matching the power requirements of each sub-unit 38 to the actual available power, as stored in power history table 44. Consequently, prediction algorithm 36 is able to predict the duration and power intensity of a current power cycle and, subsequently, dispatch the execution of one or more computational operations (i.e., one or more sub-units 38) that correspond to the predicted current power cycle. When the execution of any given sub-unit 38 is dispatched, its corresponding switch 40 is activated to receive power in the corresponding sub-unit. In this way, the probability of completing the execution of selected sub-units 38 increases and, thus, the operation of integrated circuit 22 is maximized in a given power cycle, despite operating in an intermittent power environment. Example detected power sequences and process dispatch operations are provided with reference to FIGS. 2A, 2B, 3A, 3B, and 3C. Additionally, more details of the operation of power management prediction system 20 are provided with reference to FIG. 4.

FIGS. 2A and 2B illustrate first and second process dispatch tables 60 and 62, respectively, for a first example power sequence of intermittent power source 32, in order to demonstrate examples of dispatching computational operations by use of power management prediction system 20.

In a first example, process dispatch table 60 of FIG. 2A shows a collection of “POWER CYCLES” T01 through T38. T01 through T38 are each a single time slice, such as, but not limited to, one millisecond or one microsecond. Additionally, process dispatch table 60 shows an example sequence of “AVAILABLE POWER (PWR) UNITS.” More specifically, process dispatch table 60 shows a sequence of “00000555555000005555550000055555500000” for T01 through T38, that indicates the occurrence of three power events of 5+5+5+5+5+5 each, where “0” indicates no power present and “5” indicates power present with an intensity of 5 user-defined power units (i.e., T06-T11, T17-T22, and T28-T33 represent three power events of 5+5+5+5+5+5 available power units each). Referring again to FIG. 1, if, in this example and based on the information stored in power requirements table 42, sub-units 38 a, 38 b, and 38 c each require a sequence of 5+5 power units and sub-units 38 d, 38 e, and 38 f each require a sequence of 5+5+5 power units, process dispatch table 60 of FIG. 2A shows one example dispatch sequence in the form of “SUB-UNITS EXECUTED.” More specifically and if sub-units 38 a, 38 b, 38 c, 38 d, 38 e, and 38 f are shown in process dispatch table 60 as A, B, C, D, E, and F, respectively, T06-T11 is dispatched by prediction algorithm 36 as AABBCC, T17-T22 is dispatched as DDDEEE, and T28-T33 is dispatched as FFF---. In this example, the “CONSUMED PWR UNITS” of T06-T11, T17-T22, and T28-T33 are 555555, 555555, and 555000, respectively, and the “SURPLUS PWR UNITS” for T06-T11, T17-T22, and T28-T33 are 000000, 000000, and 000555, respectively.

Alternatively, process dispatch table 62 of FIG. 2B shows the same example sequence of “AVAILABLE PWR UNITS” of “00000555555000005555550000055555500000” for T01 through T38. Additionally, if sub-units 38 a, 38 b, and 38 c each require a sequence of 5+5 power units and sub-units 38 d, 38 e, and 38 f each again require a sequence of 5+5+5 power units, process dispatch table 62 shows an alternative dispatch sequence, as determined by prediction algorithm 36. In this example, process dispatch table 62 shows that T06-T11 is dispatched by prediction algorithm 36 as AADDD-, T17-T22 is dispatched as BBEEE-, and T28-T33 is dispatched as CCFFF-. In this example, the “CONSUMED PWR UNITS” of T06-T11, T17-T22, and T28-T33 are 555550, 555550, and 555550, respectively, and the “SURPLUS PWR UNITS” for T06-T11, T17-T22, and T28-T33 are 000005, 000005, and 000005, respectively.

In the examples of process dispatch tables 60 and 62, the execution of sub-units 38 a, 38 b, 38 c, 38 d, 38 e, and 38 f may be dispatched by prediction algorithm 36 in a distributed way across the three power events of the example “AVAILABLE PWR UNITS” in such a way as to ensure the completion thereof, despite the intermittent power environment. This is possible because the information that is stored in power history table 44 allows prediction algorithm 36 to calculate the various combinations of sub-units 38 that may be executed in any given power event of a power sequence, which has been predetermined to be repeatable.

FIGS. 3A, 3B, and 3C illustrate first, second, and third process dispatch tables 64, 66, and 68, respectively, for a second example power sequence of intermittent power source 32, in order to demonstrate examples of dispatching computational operations by use of power management prediction system 20.

In a first example, process dispatch table 64 of FIG. 3A shows a collection of “POWER CYCLES” T01 through T37. T01 through T37 are each a single time slice, such as, but not limited to, one millisecond or one microsecond. Additionally, process dispatch table 64 shows an example sequence of “AVAILABLE PWR UNITS.” More specifically, process dispatch table 64 shows a sequence of “0000135753100001357531000013575310000” for T01 through T37, that indicates the occurrence of three power events of 1+3+5+7+5+3+1 each, where “0” indicates no power present and “1,” “3,” “5,” and “7” indicate power present with an intensity of 1, 3, 5, and 7, respectively, user-defined power units (i.e., T05-T11, T16-T22, and T27-T33 represent three power events of 1+3+5+7+5+3+1 available power units each). Referring again to FIG. 1, if, in this example and based on the information stored in power requirements table 42, sub-units 38 a, 38 b, and 38 c each require a sequence of 2+2 power units and sub-units 38 d, 38 e, and 38 f each require a sequence of 3+3+3 power units, process dispatch table 64 of FIG. 3A shows one example dispatch sequence in the form of “SUB-UNITS EXECUTED.” More specifically and if sub-units 38 a, 38 b, 38 c, 38 d, 38 e, and 38 f are shown in process dispatch table 60 as A, B, C, D, E, and F, respectively, prediction algorithm 36 dispatches two computational operations in parallel as follows: T05-T11 is dispatched as -AABB-- in parallel with --DDD--, T16-T22 is dispatched as -CC---- in parallel with --EEE--, and T27-T33 is dispatched as ------- in parallel with --FFF--. In this example, the “CONSUMED PWR UNITS” of T06-T11, T17-T22, and T28-T33 are 0255500, 0253300, and 0333000, respectively, and the “SURPLUS PWR UNITS” for T06-T11, T17-T22, and T28-T33 are 1102031, 1104231, and 1024531, respectively.

Alternatively, process dispatch table 66 of FIG. 3B shows the same example sequence of “AVAILABLE PWR UNITS” of “0000135753100001357531000013575310000” for T01 through T37. Additionally, if sub-units 38 a, 38 b, and 38 c each again require a sequence of 2+2 power units and sub-units 38 d, 38 e, and 38 f each again require a sequence of 3+3+3 power units, process dispatch table 66 shows an alternative dispatch sequence, as determined by prediction algorithm 36. In this example, prediction algorithm 36 again dispatches two computational operations in parallel as follows. T05-T11 is dispatched as -AA---- in parallel with --DDD--, T16-T22 is dispatched as -BB---- in parallel with --EEE--, and T27-T33 is dispatched as -CC---- in parallel with --FFF--. In this example, the “CONSUMED PWR UNITS” of T06-T11, T17-T22, and T28-T33 are 0253300, 0253300, and 0253300, respectively, and the “SURPLUS PWR UNITS” for T06-T11, T17-T22, and T28-T33 are 1104231, 1104231, and 1104231, respectively.

Alternatively, process dispatch table 68 of FIG. 3C shows the same example sequence of “AVAILABLE PWR UNITS” of “0000135753100001357531000013575310000” for T01 through T37. Additionally, if sub-units 38 a, 38 b, and 38 c each again require a sequence of 2+2 power units and sub-units 38 d, 38 e, and 38 f each again require a sequence of 3+3+3 power units, process dispatch table 66 shows an alternative dispatch sequence, as determined by prediction algorithm 36. In this example, prediction algorithm 36 dispatches computational operations as follows: T05-T11 is dispatched as -AADDD-, T16-T22 is dispatched as -BBEEE-, and T27-T33 is dispatched as -CCFFF-. In this example, the “CONSUMED PWR UNITS” of T06-T11, T17-T22, and T28-T33 are 0253300, 0253300, and 0253300, respectively, and the “SURPLUS PWR UNITS” for T06-T11, T17-T22, and T28-T33 are 1134201, 1134201, and 1134201, respectively.

In the examples of process dispatch tables 64, 66, and 68, the execution of sub-units 38 a, 38 b, 38 c, 38 d, 38 e, and 38 f is dispatched by prediction algorithm 36 in a distributed way across the three power events of the example “AVAILABLE PWR UNITS” in such a way as to ensure the completion thereof, despite the intermittent power environment. This is possible because the information that is stored in power history table 44 allows prediction algorithm 36 to calculate the various combinations of sub-units 38 that may be executed in any given power event of a power sequence, which has been predetermined to be repeatable.

FIG. 4 illustrates a flow diagram of a method 70 of predicting power events in an intermittent power environment and dispatching computational operations by use of power management prediction system 20 of FIG. 1. Method 70 includes, but is not limited to, the following steps.

At step 72, the known power requirements of each computational operation, such as each sub-unit 38, may be stored in power requirements table 42 in storage device 28. For example, a power requirement of 20 milliwatts for a duration of 3 milliseconds may be required to execute the computational operation that is represented by sub-unit 38 a. Method 70 proceeds to step 74.

At step 74, the intermittent power source, such as intermittent power source 32, may be monitored for any user-defined period of time by any conventional means, such as by, but not limited to, power monitor circuit 34, in order to generate a history log, which is stored in power history table 44 in storage device 28. Method 70 proceeds to step 76.

At step 76, a current or subsequent power event, n, may be predicted by prediction algorithm 36 of controller 24 based on the knowledge of one or more previous (e.g., n-1 to n-x) power events stored in power history table 44 in storage device 28. Method 70 proceeds to step 78.

At step 78, prediction algorithm 36 of controller 24 retrieves the actual power requirements of one or more computational operations (e.g., one or more sub-units 38) from power requirements table 42 in storage device 28. Method 70 proceeds to step 80.

At step 80, under the control of prediction algorithm 36 of controller 24, the predicted power event, as determined by analyzing the contents of power history table 44, and the actual power requirements, as retrieved by power requirements table 42, may be compared in order to determine whether the predicted power event is suitable (e.g., in intensity and duration) to satisfy the actual power requirements of one or more sub-units 38. In doing so, the characteristics of the current power event may be compared against those from the predicted power event. Method 70 proceeds to step 82.

At decision step 82, if is it determined that a predicted power event satisfies the actual power requirements of at least one sub-unit 38, method 70 proceeds to step 84. However, if is it determined that the predicted power event does not satisfy the actual power requirements of at least one sub-unit 38, method 70 proceeds to step 86.

At step 84, prediction algorithm 36 of controller 24 may dispatch one or more computational operations, e.g., one or more sub-units 38, that correspond to one or more actual power events of intermittent power source 32. Method 70 ends.

At step 86, in the case of an incorrect prediction, power management prediction system 20, under the control of prediction algorithm 36 of controller 24, may perform an error recovery operation. For example, prediction algorithm 36 may treat the current power event as a new power event and, thus, prediction algorithm 36 enters a training mode. In this situation (such as at initialization of the system), the characteristics of the current power event are analyzed and stored in power history table 44. The current processing occurs normally, except that the results of every stage (clock cycle of clock generator 30) may be stored into storage device 28. Although this may be an inefficient use of the available power, the power used for processing will not be wasted if the next cycle does not complete. Method 70 ends.

In summary and referring to FIGS. 1 through 4, power management prediction system 20 and method 70 provide a means for predicting power events in an intermittent power environment and dispatching computational operations of an integrated circuit accordingly. In particular, power management prediction system 20 executes computational operations in an intermittent power environment by storing information on previous power events in power history table 44 of storage device 28 and using this information to predict (via prediction algorithm 36) the strength and duration of a present power event upon detection. Power management prediction system 20 uses the prediction, as well as stored data (e.g., power consumption statistics) on each sub-unit 38 per computational operation, in order to determine the amount of computation to be performed in the present cycle. Subsequently, power management prediction system 20 dispatches sequentially or in parallel to the appropriate logical sub-units 38. Should the power event prediction be incorrect, provision is made for the storage of intermediate data in storage device 28 for recovery.

FIG. 5 shows a block diagram of an example design flow 50. Design flow 50 may vary depending on the type of IC being designed. For example, a design flow 50 for building an application specific IC (ASIC) may differ from a design flow 50 for designing a standard component. Design structure 52 is preferably an input to a design process 51 and may come from an IP provider, a core developer, or other design company or may be generated by the operator of the design flow, or from other sources. Design structure 52 comprises circuit 22 in the form of schematics or HDL, a hardware-description language (e.g., Verilog, VHDL, C, etc.). Design structure 52 may be contained on one or more machine readable medium. For example, design structure 52 may be a text file or a graphical representation of circuit 22. Design process 51 preferably synthesizes (or translates) circuit 22 into a netlist 58, where netlist 58 is, for example, a list of wires, transistors, logic gates, control circuits, I/O, models, etc. that describes the connections to other elements and circuits in an integrated circuit design and recorded on at least one of machine readable medium. This may be an iterative process in which netlist 58 is resynthesized one or more times depending on design specifications and parameters for the circuit.

Design process 51 may include using a variety of inputs; for example, inputs from library elements 53 which may house a set of commonly used elements, circuits, and devices, including models, layouts, and symbolic representations, for a given manufacturing technology (e.g., different technology nodes, 32 nm, 45 nm, 90 nm, etc.), design specifications 54, characterization data 55, verification data 56, design rules 57, and test data files 59 (which may include test patterns and other testing information). Design process 51 may further include, for example, standard circuit design processes such as timing analysis, verification, design rule checking, place and route operations, etc. One of ordinary skill in the art of integrated circuit design can appreciate the extent of possible electronic design automation tools and applications used in design process 51 without deviating from the scope and spirit of the invention. The design structure of the invention is not limited to any specific design flow.

Design process 51 preferably translates an embodiment of the invention as shown in FIG. 1, along with any additional integrated circuit design or data (if applicable), into a second design structure 60. Design structure 60 resides on a storage medium in a data format used for the exchange of layout data of integrated circuits (e.g. information stored in a GDSII (GDS2), GL1, OASIS, or any other suitable format for storing such design structures). Design structure 60 may comprise information such as, for example, test data files, design content files, manufacturing data, layout parameters, wires, levels of metal, vias, shapes, data for routing through the manufacturing line, and any other data required by a semiconductor manufacturer to produce an embodiment of the invention as shown in FIG. 1. Design structure 60 may then proceed to a stage 61 where, for example, design structure 60: proceeds to tape-out, is released to manufacturing, is released to a mask house, is sent to another design house, is sent back to the customer, etc.

An exemplary embodiment has been disclosed above and illustrated in the accompanying drawings. It will be understood by those skilled in the art that various changes, omissions and additions may be made to that which is specifically disclosed herein without departing from the spirit and scope of the present invention. 

1. A design structure embodied in a machine readable storage medium used in a design process of a power management prediction system for use with a power source that produces power events, the design structure of said system comprising: a monitor connectable to the power source for monitoring the power source and producing a power history table of power events previously produced by the power source; computation circuitry; a power requirements table containing power requirements information for said computational circuitry; and a controller connected to said computation circuitry, said power history table and said power requirements table, said controller calculating a predicted power cycle based on said power events in said power history table and enabling power to said computation circuitry based on said predicted power cycle and said power requirements information.
 2. The design structure of claim 1, wherein the design structure comprises a netlist, which describes the circuit.
 3. The design structure of claim 1, wherein the design structure resides on storage medium as a data format used for the exchange of layout data of integrated circuits.
 4. The design structure of claim 1, wherein the design structure includes at least one of test data files, characterization data, verification data, or design specifications.
 5. A design structure embodied in a computer readable storage medium for performing a method of managing power prediction for computational operations, the design structure comprising: a means for storing a set of power requirements for one or more computational operations; a means for monitoring a power source and creating a power history table of power events previously produced by the power source; a means for predicting a subsequent power event based on power events in the power history table; a means for retrieving the set of power requirements for one or more computational operations; and a means for comparing the set of power requirements with power events in the power history table to determine if the set of power requirements are met for one or more computational operations. 